Content storage mapping

ABSTRACT

A data storage method and system. The method includes defining, by a computing system, a meta-object, a schema based structured definition for the meta-object, and a taxonomy with configuration data. The computing system creates content associated with the taxonomy and associates topics of the content with a logical storage room representations. Reference coordinates associated with the logical storage room representations are associated with the taxonomy. The computing system generates updated configuration data that includes the reference coordinates and a uniform resource identifier associated with the content is generated. The computing system generates an account associated with the meta-object for a user. Metering charges for usage of the account and a report associated with the account and usage are generated.

This application is a continuation application claiming priority to Ser.No. 13/964,207 filed Aug. 12, 2013 which is a continuation applicationclaiming priority to Ser. No. 13/448,511 filed Apr. 17, 2012, now U.S.Pat. No. 8,554,777, issued Oct. 8, 2013; which is a continuationapplication claiming priority to Ser. No. 12/606,260, filed Oct. 27,2009, now U.S. Pat. No. 8,229,936, issued Jul. 24, 2012.

FIELD

The present invention relates to a method and associated system forstoring and retrieving distributed data.

BACKGROUND

Accessing information typically comprises an inefficient process withlittle flexibility. Systems are typically required to access and viewinformation at a single location which may be inefficient. Accessinginformation at a single location at a single time may be very timeconsuming.

SUMMARY

The present invention provides a method comprising: defining, by acomputing system, a user accessible meta-object referencing contextualcontent, wherein said user accessible meta-object comprises a functionaloperation referenced object, a service referenced object, or a contentspecific referenced object; defining, by said computing system, a schemabased structured definition for said user accessible meta-object;defining, by said computing system from said schema based structureddefinition, a predefined user access content mapped hierarchicaltaxonomy and a configuration data map associated with said predefineduser access content mapped hierarchical taxonomy; determining, by saidcomputing system, that content is required for said computing system;creating, by a processor of said computing system, said content, whereinsaid content comprises user accessible contextual content associatedwith said predefined user access content mapped hierarchical taxonomy;associating, by said computing system, user accessible topics ofrelevant tangible content of said content with specified logical storageroom representations, wherein each storage room of said specifiedlogical storage room representations comprises contextual contentstorage address spaces; associating, by said computing system, referencecoordinates with said predefined user access content mapped hierarchicaltaxonomy, wherein said reference coordinates are associated with saidspecified logical storage room representations; determining, by saidcomputing system, a change associated with a relative point of viewassociated with each node of said predefined user access content mappedhierarchical taxonomy; updating, by said computing system, saidconfiguration data map, wherein said updating said configuration datamap comprises generating updated configuration data, wherein saidupdated configuration data comprises reference coordinate pointerspointing to the contextual content storage address spaces, and whereinthe contextual content storage address spaces are comprised by aplurality of different storage mediums and a plurality of differentphysical storage locations; generating, by said computing system, auniform resource identifier (URI) associated with said content enablinga direct internal access mapping to the contextual content storageaddress spaces associated with said reference coordinate pointers;determining, by said computing system, metering charges for usage of anaccount per paid subscription to the user accessible contextual content;applying, by said computing system, key performance indicators totransactional analysis usage patterns of said user accessible contextualcontent; generating, by said computing system, a report associated withsaid account and said usage; and storing, by said computing system, saidreport.

The present invention provides a computing apparatus comprising aprocessor coupled to a computer-readable memory unit, said memory unitcomprising instructions that when executed by the processor implements amethod comprising: defining, by said computing system, a user accessiblemeta-object referencing contextual content, wherein said user accessiblemeta-object comprises a functional operation referenced object, aservice referenced object, or a content specific referenced object;defining, by said computing system, a schema based structured definitionfor said user accessible meta-object; defining, by said computing systemfrom said schema based structured definition, a predefined user accesscontent mapped hierarchical taxonomy and a configuration data mapassociated with said predefined user access content mapped hierarchicaltaxonomy; determining, by said computing system, that content isrequired for said computing system; creating, by a processor of saidcomputing system, said content, wherein said content comprises useraccessible contextual content associated with said predefined useraccess content mapped hierarchical taxonomy; associating, by saidcomputing system, user accessible topics of relevant tangible content ofsaid content with specified logical storage room representations,wherein each storage room of said specified logical storage roomrepresentations comprises contextual content storage address spaces;associating, by said computing system, reference coordinates with saidpredefined user access content mapped hierarchical taxonomy, whereinsaid reference coordinates are associated with said specified logicalstorage room representations; determining, by said computing system, achange associated with a relative point of view associated with eachnode of said predefined user access content mapped hierarchicaltaxonomy; updating, by said computing system, said configuration datamap, wherein said updating said configuration data map comprisesgenerating updated configuration data, wherein said updatedconfiguration data comprises reference coordinate pointers pointing tothe contextual content storage address spaces, and wherein thecontextual content storage address spaces are comprised by a pluralityof different storage mediums and a plurality of different physicalstorage locations; generating, by said computing system, a uniformresource identifier (URI) associated with said content enabling a directinternal access mapping to the contextual content storage address spacesassociated with said reference coordinate pointers; determining, by saidcomputing system, metering charges for usage of an account per paidsubscription to the user accessible contextual content; applying, bysaid computing system, key performance indicators to transactionalanalysis usage patterns of said user accessible contextual content;generating, by said computing system, a report associated with saidaccount and said usage; and storing, by said computing system, saidreport.

The present invention provides a computer program product, comprising acomputer readable storage device storing a computer readable programcode, said computer readable program code configured to perform methodupon being executed by a computer processor of a computing system, saidmethod comprising: defining, by said computing system, a user accessiblemeta-object referencing contextual content, wherein said user accessiblemeta-object comprises a functional operation referenced object, aservice referenced object, or a content specific referenced object;defining, by said computing system, a schema based structured definitionfor said user accessible meta-object; defining, by said computing systemfrom said schema based structured definition, a predefined user accesscontent mapped hierarchical taxonomy and a configuration data mapassociated with said predefined user access content mapped hierarchicaltaxonomy; determining, by said computing system, that content isrequired for said computing system; creating, by a processor of saidcomputing system, said content, wherein said content comprises useraccessible contextual content associated with said predefined useraccess content mapped hierarchical taxonomy; associating, by saidcomputing system, user accessible topics of relevant tangible content ofsaid content with specified logical storage room representations,wherein each storage room of said specified logical storage roomrepresentations comprises contextual content storage address spaces;associating, by said computing system, reference coordinates with saidpredefined user access content mapped hierarchical taxonomy, whereinsaid reference coordinates are associated with said specified logicalstorage room representations; determining, by said computing system, achange associated with a relative point of view associated with eachnode of said predefined user access content mapped hierarchicaltaxonomy; updating, by said computing system, said configuration datamap, wherein said updating said configuration data map comprisesgenerating updated configuration data, wherein said updatedconfiguration data comprises reference coordinate pointers pointing tothe contextual content storage address spaces, and wherein thecontextual content storage address spaces are comprised by a pluralityof different storage mediums and a plurality of different physicalstorage locations; generating, by said computing system, a uniformresource identifier (URI) associated with said content enabling a directinternal access mapping to the contextual content storage address spacesassociated with said reference coordinate pointers; determining, by saidcomputing system, metering charges for usage of an account per paidsubscription to the user accessible contextual content; applying, bysaid computing system, key performance indicators to transactionalanalysis usage patterns of said user accessible contextual content;generating, by said computing system, a report associated with saidaccount and said usage; and storing, by said computing system, saidreport.

The present invention advantageously provides a simple method andassociated system capable of saving information.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a system for storing and retrieving distributed data,in accordance with embodiments of the present invention.

FIG. 2 including FIGS. 2A-2C, illustrates a data (layer) model, inaccordance with embodiments of the present invention.

FIGS. 3 and 4 illustrate an implementation example for enabling thesystem of FIG. 1 to represent hierarchal taxonomies as a relative pointof view, in accordance with embodiments of the present invention.

FIG. 5 illustrates a flowchart describing an algorithm used by thesystem of FIG. 1 for enabling a process for storing and retrievingdistributed data, in accordance with embodiments of the presentinvention.

FIG. 6 illustrates a flowchart describing an algorithm used by thesystem of FIG. 1 for enabling a process for accessing distributed data,in accordance with embodiments of the present invention.

FIGS. 7-15 illustrate flowcharts detailing various steps of thealgorithm of FIG. 5, in accordance with embodiments of the presentinvention.

FIGS. 16-19 illustrate flowcharts detailing various steps of thealgorithm of FIG. 6, in accordance with embodiments of the presentinvention.

FIG. 20 illustrates an application framework implemented by the systemof FIG. 1, in accordance with embodiments of the present invention.

FIG. 21 illustrates a computer apparatus for storing and retrievingdistributed data, in accordance with embodiments of the presentinvention.

DETAILED DESCRIPTION

FIG. 1 illustrates a system 5 for storing and retrieving distributeddata, in accordance with embodiments of the present invention. System 5comprises a distributed object-oriented retrieval and storage (DOORS)system for providing (i.e., via a data access layer as described anddefined, infra) a single universal interface that provides access totangible related data (from a plurality of different types of storagemediums and different physical storage locations) from a sameintersected base topic. The DOORS system provides a universal 3dimensional (3D) relative positioning interface to a framework thatenables a standardized means of simultaneous access, retrieval, storage,and management capabilities of diverse and federated data sources (i.e.,content storage address spaces for data are comprised by differentstorage mediums and different physical storage locations). A sharedaddress space points to multiple different storage mediums and physicalstorage locations. A data access layer (i.e., as illustrated anddescribed in detail with respect to FIG. 20, infra) comprises threesub-layers:

1. A DOORS access-bus (H1) via REST (representational state transferarchitectural style for large scale software design) style addressing.2. DOORS data access logic components (H2).3. A DOORS service agent component (H3).Each one of the sub-layers (H1, H2, and H3) enables separate discreteresponsibilities. Collectively the sub-layers (H1, H2, and H3) provide aunique means of providing simultaneous multi-dimensional perspectivestorage and retrieval capabilities of a referenced user accessiblemeta-object (resource) associated with contextual related content(retrieved simultaneously) from a plurality of different storage mediumsand different physical storage locations. A user accessible meta-objectis defined herein as a functional operation, a service, or a contentspecific referenced object that may be assessed by a user.

System 5 provides a single reference point (point of view as describedin detail with respect to FIGS. 3 and 4, infra) allowing simultaneousaccess to multiple pointers that point to multiple address spaces(associated with a plurality of different storage mediums and differentphysical storage locations) each comprising different data as opposed toa single reference point allowing access to only one pointer that pointsto only a single address space associated with a single storage mediumor location. A virtual data architectural data layer (e.g., see FIGS. 2and 20) provides a standardized integration system to expose data as aservice. System 5 provides a common means to integrate to all forms ofdata resources and data flowing through an enterprise operationenvironment by providing a commonly referenced interface therebyallowing system 5 to:

1. Enable an organization a capability to leverage valid data acrossapplications and operational domains in real-time.2. Provide a common means to manage provisioning of traditional andnon-traditional logical and physical storage resources.3. Provide a common means of metering and cost accounting for usage ofdata and logical (and physical) storage resources.

System 5 of FIG. 1 comprises a computing apparatus 8 a connected to acomputing system 10 through a network 7. Network 7 may comprise any typeof network including, inter alia, a local area network, (LAN), a widearea network (WAN), the Internet, etc. Computing apparatus 8 a maycomprise any type of computing apparatus including, inter alia, apersonal computer, a laptop computer, a computer terminal, etc.Computing apparatus 8 a may comprise a single computing apparatus or aplurality of computing apparatuses. Computing apparatus 8 a is used byend users for communicating with (e.g., entering data) computing system10. Computing system 10 may comprise any type of computing system(s)including, inter alia, a personal computer (PC), a server computer, adatabase computer, etc. Computing system 10 is used to store (andretrieve data from computing apparatus 8 a). Computing system 10 maycomprise a multi-sourced user accessible context and content driven dataaccess computer comprising an application architectural component thatperforms the work of intelligent retrieval and storage and navigationcoordination of contextual content from multiple storage locations andtypes. Computing system 10 comprises a memory system 14. Memory system14 may comprise a single memory system. Alternatively, memory system 14may comprise a plurality of memory systems. Memory system 14 comprises asoftware application 18 and a database 12. Database 12 may comprisemultiple databases. Database 12 comprises all retrieved data (i.e.,retrieved from computing apparatus 8 a) and any generated data (e.g.,data layer model 200 as described with respect to FIG. 2). System 5comprises a DOORS system providing a universal natural 3D relativepositioning (i.e., X, Y, Z axis type storage as described with respectto FIGS. 3 and 4) interface to a framework that enables a standardizedmeans of access, retrieval, storage, and management capabilities ofdiverse and federated data sources (i.e., a plurality of differentstorage mediums and different physical storage locations) across anenterprise model through a virtual architectural data access layer.Additionally, a 3D relative positioning of a specific area of a topicenables a user to pivot and transverse to its semantic relationshipsalong an X, Y, and Z axis (i.e., a single point of view pointing tomultiple pointers X, Y, and Z). System 5 enables a single intersectionpoint between the X, Y, and Z axis to hold a different value dependingon a perspective of a relative point of view. The DOORS system allowsfor increased storage capacity of various data at a same address spacedepending on a point of view perspective.

Software application 18 enables the following functions associated withdata storage and retrieval:

1. Providing a single common style 3D spatial interface to enterprisedata storage and retrieval.2. Providing a single common style 3D spatial interface to enterprisedata management.3. Using a standardized REST Style resource addressing notation.4. Enabling data integration across logical and physical barriers (i.e.,across a plurality of different storage mediums and different physicalstorage locations).5. Enabling fully extensive enterprise data integration, therebycreating hybrid information assets.6. Enabling a basic standard for metering and cost accounting resources.7. Enabling a standard base measurement unit for monitoring.8. Enable multiple translation of a same reference point, depending on aperspective of point of view (POV).9. Allowing a multi-perspective 3D Point of view design to be translatedto a logical multiple layer storage translation at a shared addressspace (i.e., a shared address space points to multiple different storagemediums and physical storage locations).10. Enabling persisted information (i.e., regardless of how it isstored) to be readily addressable, accessible, and potentially consumedby all integrated services (both internal and external) across allapplication layers depending on applied security controls.

FIG. 2 including FIGS. 2A-2C, illustrates a data access (layer) model200, in accordance with embodiments of the present invention. Data model200 in FIG. 2 comprises a graphical representation of a DOORS datamodel. Data model 200 comprises the following components:

1. An account management component 202 for enabling management of useraccounts through creation of users, accounts, and mapping ofmeta-objects (i.e., a reference object characterized by information)associated with use of an account.2. A metering component 204 for enabling rates to be applied to usage ofcontent related meta-objects based on access time to a logical datastorage room. A logical data storage room is defined herein as a localrepresentation of a meta-object storage container (comprised by multipledifferent storage mediums and physical storage locations) and ischaracterized by an associated topic.3. A provisioning component 210 for allocating meta-objects and logicalstorage room representations comprised by multiple different storagemediums and physical storage locations (i.e., defined within anamespace, a domain, and a sub-domain) based on existing availability.4. A representation state transfer (REST) interface 208 for exposingmeta-objects through an infinite number of uniform resource identifiers(i.e., URI) thereby enabling the DOORS system an addressability to scaleaccordingly with newly added provisioned meta-objects.5. A viewpoints component 209 for enabling a multi-perspective filteringof a POV (i.e., X, Y, Z) content reference with applied context (e.g.,who, what, where, when, how, why, etc).6. A 3D Pivotable Access component 212 for represents X, Y, Zcoordinates and associated pointers to content (i.e., address spaces).7. An internal addressing component 214 for keeping track of internalpointers to content regardless of pointer type (e.g., pointer to file,pointer to column, pointer to memory address, etc) and storage type.8. A configuration component 224 for generating mapping to between X, Y,Z coordinates and locations on a predefined user access content mappedhierarchal taxonomy.9. A schema management component 228 for enabling a creation andmanagement of defined schema based structure definitions used to definea hierarchical structure of a meta-object relationship.10. A discovery component 220 for enabling mapping of topics to logicalstorage room representations and generating a searchable record entrywithin a discovery data store.11. An analysis & reporting component 218 for enabling an association ofoperational metrics and key performance indicators (KPI) to be appliedvia transactional analysis usage patterns of all DOORS related data andthe reporting of analysis through defined reporting channels (e.g.,reports, dashboards, messaging, etc).

FIGS. 3 and 4 illustrate an implementation example for enabling system 5of FIG. 1 to represent hierarchal taxonomies as a relative point ofview, in accordance with embodiments of the present invention. In FIGS.3 and 4, data retrieval, storage, and data resource management planning(e.g., procurement, provisioning, capacity planning, space managementetc.) are each represented in separate hierarchical taxonomies. Eachnode on the taxonomy represents a logical storage room representationcomprised by a plurality of different storage mediums and physicalstorage locations (e.g., see rooms 302, 304, and 308 in FIG. 3 or rooms402, 404, and 408 in FIG. 4). This hierarchical taxonomy is segmented byits interdependency relationship intersections to other taxonomies. Theenumerated items (e.g., 001, 002, 003 in FIG. 3 or 009, 010, 011, etc inFIG. 4) in FIGS. 3 and 4 represent separate parent taxonomies (addressspaces). As a user navigates through taxonomies topics, the usernavigates between rooms 302, 304, and 308 or rooms 402, 404, and 408.The term DOORS is used metaphorically as entry point into each of therooms via a standardized interface. Upon entering a room, the user has arelative 3D (simultaneous) point of view (spatial definition) whichrepresents a three point intersection (i.e., X, Y, Z coordinates orpointers) on 3 different related intersection taxonomy nodes that pointto 3 different address spaces. As the user progresses through each nodeon the taxonomy (i.e., a room), a relative point of view (POV) changes.A view from a point of view depends upon the user's perspective. A usermay be in multiple storage room representations (i.e., different storagemediums and physical storage locations) simultaneously supportingmultiple perspectives (i.e., for address spaces) from a single point ofview. This will exponentially enable the integration of variousperspective points of views (i.e., to different address spaces) in dataprocessing.

FIG. 3 illustrates a logical diagram 300 comprising X, Y, Z, coordinates(i.e., spatial definition reference points to different pointers) and amulti-dimensional perspective (1-n) point of view. For example,hierarchal relationships illustrated in FIG. 3 include the followingaddress spaces that may be simultaneously accessed via multiple pointersX, Y, and Z from a single POV:

001—Files consisting of records and records consisting of fields.002—Tables consisting of rows and rows consisting of columns.003—Queues containing messages and messages containing fields.004—Mailbox containing messages. A message may contain subjects.005—Smart physical component comprise sensors. Sensors read and storeattributes.006—Software components contain objects that comprise attributes.007—Software components contain objects comprising methods.008—A process comprises one or more activities having one or more tasks.

As an example, address space 001.Field (i.e., on the X-axis or pointer),address space 001.Record (i.e., on the Y-axis or pointer), and addressspace 001.File (i.e., on the Z-axis or pointer) may be simultaneouslyviewed and accessed.

Logical diagram 300 represents three dimensional planes (i.e., Y plane302 of a room, an X plane 304 of a room, and a Z plane 308 of a room) ofa logical storage room representation. A room is defined herein as alogical reference to a specific topic that a user would have access touse within system 5 of FIG. 1. X, Y, and Z coordinates in logicaldiagram 300 represent each dimensional plane of a three dimensional POV(i.e., Y plane 302 of a room, an X plane 304 of a room, and a Z plane308 of a room). Collectively, a combination of X, Y, and Z coordinatesrepresent a specified POV within a viewing space. Enumerated subjectareas (001-008) are defined differently for each dimensional plane (X,Y, and Z) of a user accessible topic (i.e., room). For example, if aTopic of a Room is “Smart Devices”, subject areas 005 represent amulti-dimensional hierarchical relationship of content relevant to thetopic “Smart Devices”. For Example: Z(005) subject area comprises areferenced component within a smart device, Y(005) comprises a sensorwithin the component, and X(005) comprises defined attributes of thesensors. In this example (i.e., in reference to this room), as the usermoves along the Z axis, he/she moves between various components. As theuser moves along the Y axis, his/her references to specific a sensorchanges. As the user moves along the X axis his/her references to sensorattributes changes. Therefore in this example, the point of view (POV)would represent a specific attribute within a specific sensor within acertain component being referenced with the topic of smart devices.

FIG. 4 illustrates X, Y, Z, coordinates (i.e., spatial definitionreference points) and a multi-dimensional perspective (1-n) point ofview. For example, hierarchal relationships illustrated in FIG. 4include the following address spaces that may be simultaneously accessedvia multiple pointers X, Y, and Z from a single POV:

009—Directory consisting of files and files consisting of records.010—Database consisting of tables and tables consisting of rows.011—A queue manager coordinates queue and queue coordinate messages.012—An electronic post office contains mailboxes comprising messages.013—A smart physical device comprising smart physical components havingsensors.014—A service exposes a software component consisting of objects.015—Workflows contain staged processes.

As an example, address space 009.Record (i.e., on the X-axis orpointer), address space 009.File (i.e., on the Y-axis or pointer), andaddress space 009.Directory (i.e., on the Z-axis or pointer) may besimultaneously viewed and accessed.

Logical diagram 400 represents three dimensions (i.e., Y plane 402 of aroom, an X plane 404 of a room, and a Z plane 408 of a room) of alogical storage room representation. For example, if a Topic of a Roomis “Smart Grid”, subject areas 005 represent a multi-dimensionalhierarchical relationship of content relevant to the topic “Smart Grid”.In this example, Z(005) subject area comprises a referenced smart devicewithin the “Smart Grid”, Y(005) comprises a component within the smartdevice, and X(005) comprises a sensor with the component. Logicaldiagram 400 of FIG. 4 represents a next level within a hierarchicaltaxonomy of related content between rooms. Taxonomies exist within roomand between rooms and as the user moves between rooms, they traversethrough adjoining taxonomies. Within rooms, configuration data providescross reference mapping of the X, Y, and Z coordinates tomulti-dimensional subject areas as defined with room taxonomies. TheDOORS system manages this level of complexity and simultaneousmulti-dimensional navigational access through its unique data accesslayer.

Additionally, FIGS. 3 and 4 may be used to represent a physical use of aDOORS system.

As a first example, physical disk drives have tracks and cylinders. In aDOORS system, a disk may represent a Z axis, a cylinder may represent aY axis, and tracks may represent an X axis.

As a second example, an aggregation of storage devices into a storageaccess network (SAN) may include a SAN representing a Z axis reference,a list of storage devices within the SAN representing a Y axisreference, and a disk within the storage device representing an X axisreference. A SAN comprises an architecture to attach remote computerstorage devices (such as disk arrays, tape libraries, and opticaljukeboxes) to servers in such a way that the devices appear as locallyattached to the operating system. A SAN as described in the secondexample enables multiple translation of a same reference point,depending on a perspective of point of view (POV). A multi-perspective3D Point of view design may be translated to a logical multiple layerstorage translation at a shared address space and increase storagecapacity with the use of more sophisticated translation pointers.

FIG. 5 illustrates a flowchart describing an algorithm used by system 5of FIG. 1 for enabling a process for storing and retrieving distributeddata simultaneously across multiple data storage mediums and differentphysical storage locations, in accordance with embodiments of thepresent invention. In step 502, a computing system (e.g., computingsystem 5 of FIG. 1) defines a user accessible meta-object referencingcontextual content. The user accessible meta-object may comprise afunctional operation related to a functional operation object, a serviceobject or a content specific referenced object. In step 504, thecomputing system defines a schema based structured definition for theuser accessible meta-object. In step 506, computing system defines(i.e., from the schema based structured definition) a predefined useraccess content mapped hierarchical taxonomy and a configuration data mapassociated with the predefined user access content mapped hierarchicaltaxonomy. In step 508, the computing system determines that content isrequired for the computing system and creates the content (i.e.,comprising user accessible contextual content associated with thepredefined user access content mapped hierarchical taxonomy). In step510, the content is associated with the content mapped hierarchicaltaxonomy. In step 512, the computing system associates user accessibletopics of relevant tangible content of the content with specifiedlogical storage room representations comprising contextual contentstorage address spaces. In step 514, the computing system associatesreference coordinates with the predefined user access content mappedhierarchical taxonomy. The reference coordinates are associated with thespecified logical storage room representations. In step 516, thecomputing system updates the configuration data map. The updatingprocess includes generating updated configuration data. The updatedconfiguration data comprises reference coordinate pointers pointing tothe contextual content storage address spaces. The contextual contentstorage address spaces are comprised by a plurality of different storagemediums and a plurality of different physical storage locations. In step518, the computing system generates a uniform resource identifier (URI)associated with the content. The URI is associated with the content andenables a direct internal access mapping to the contextual contentstorage address spaces associated with the reference coordinatepointers. In step 520, the computing system generates an account for auser. The account is associated with the user accessible meta-object. Instep 522, the computing system determines metering charges for usage ofthe account. In step 524, the computing system analyzes the account andthe usage and generates and stores a report associated with theanalysis.

FIG. 6 illustrates a flowchart describing an algorithm used by system 5of FIG. 1 for enabling a process for simultaneously accessingdistributed data across multiple data storage mediums and differentphysical storage locations, in accordance with embodiments of thepresent invention. In step 602, a computing system (e.g., computingsystem 5 of FIG. 1) generates a call through an application programinterface (API) and determines (i.e., using the API in response to thecall) an internal functionality of the computing system. In step 604,the computing system presents (in response to the call) a useraccessible content filter perspective user interface to a user andreceives (from the user through the user accessible content filterperspective user interface) known user accessible input data associatedwith specified user accessible filter perspective content. In step 608,the computing system determines (in response to the known useraccessible input data) a plurality of address space coordinatescross-referenced to the specified user accessible filter perspectivecontent. Additionally, the computing system simultaneously retrieves(i.e., from a plurality of different storage sources in response to theplurality of address space coordinates) the specified user accessiblefilter perspective content. In step 610, the computing system determines(in response the known user accessible input data) a specified filteredperspective for viewing the specified user accessible filter perspectivecontent. In step 612, the computing system presents to the user, thespecified user accessible filter perspective content using the specifiedperspective.

FIG. 7 illustrates a flowchart detailing step 502 of the algorithm ofFIG. 5, in accordance with embodiments of the present invention. In step702, the computing system defines a namespace for the user accessiblemeta-object. In step 704, the computing system defines a domain for thenamespace. In step 708, the computing system defines a sub-domainassociated with the domain. In step 710, the computing system classifiesa type for the user accessible meta-object. In step 712, the computingsystem defines attributes for the user accessible meta-object. In step714, the computing system generates mapping data associated with theURI.

FIG. 8 illustrates a flowchart detailing step 504 of the algorithm ofFIG. 5, in accordance with embodiments of the present invention. In step802, the computing system defines elements associated with the schemabased structured definition. In step 804, the computing system definesattributes associated with the elements.

FIG. 9 illustrates a flowchart detailing step 508 of the algorithm ofFIG. 5, in accordance with embodiments of the present invention. In step902, the computing system determines a content type for the content. Instep 904, the computing system determines a sub-domain associated withthe user accessible meta-object. In step 908, the computing systemdetermines a domain associated with the sub-domain. In step 910, thecomputing system determines a namespace (i.e., an identifier specifyinga location in storage) associated with the domain. In step 912, thecomputing system generates an entry in a provisioning table. The entryis associated with the content.

FIG. 10 illustrates a flowchart detailing step 510 of the algorithm ofFIG. 5, in accordance with embodiments of the present invention. In step1002, the computing system updates the predefined user access contentmapped hierarchical taxonomy with the topic. In step 1004, the computingsystem updates the predefined user access content mapped hierarchicaltaxonomy with elements associated with the schema based structureddefinition. In step 1008, the computing system updates the predefineduser access content mapped hierarchical taxonomy with attributesassociated with the elements.

FIG. 11 illustrates a flowchart detailing step 514 of the algorithm ofFIG. 5, in accordance with embodiments of the present invention. In step1102, the computing system cross references an X-coordinate, aY-coordinate, and a Z-coordinate (i.e., the reference coordinates). Instep 1104, the computing system determines an X-pointer associated withthe predefined user access content mapped hierarchical taxonomy. In step1108, the computing system determines a Y-pointer associated with thepredefined user access content mapped hierarchical taxonomy. In step1110, the computing system determines a Z-pointer associated with thepredefined user access content mapped hierarchical taxonomy.

FIG. 12 illustrates a flowchart detailing step 516 of the algorithm ofFIG. 5, in accordance with embodiments of the present invention. In step1202, the configuration data is updated with coordinates for thespecified logical storage room representations. In step 1204, thecomputing system associates the X-coordinate, the Y-coordinate, and theZ-coordinate with the X-pointer, the Y-pointer, and the Z-pointer,respectively. In step 1206, the computing system updates theconfiguration data with the X-pointer, the Y-pointer, and the Z-pointer.

FIG. 13 illustrates a flowchart detailing step 518 of the algorithm ofFIG. 5, in accordance with embodiments of the present invention. In step1302, the computing system selects a door (i.e., an access point)associated with a specified logical storage room representation. In step1304, the computing system selects the specified logical storage roomrepresentation. In step 1308, the computing system determines aplurality of meta-objects associated with the specified logical storageroom representation. In step 1310, the computing system determines aplurality of sub-domains associated with the plurality of meta-objects.In step 1312, the computing system determines a plurality of domainsassociated with the plurality of sub-domains. In step 1315, thecomputing system determines a namespace associated with the plurality ofdomains. In step 1318, the computing system generates a path associatedwith the URI. In step 1320, the computing system generates an entry in ameta-object repository. The entry is associated with the URI.

FIG. 14 illustrates a flowchart detailing steps 520 and 522 of thealgorithm of FIG. 5, in accordance with embodiments of the presentinvention. In step 1402, the computing system determines a plurality ofaccounts that have access to the specified logical storage roomrepresentation. In step 1404, the computing system calculates an accountaccess time for a plurality of objects associated with the specifiedlogical storage room representation. In step 1408, the computing systemcalculates the metering charges by multiplying the account access timeby a rate charged for access to the specified logical storage roomrepresentation. In step 1410, the computing system associates theaccount with the usage. In step 1414, the computing system generates aninvoice associated with the metering charges.

FIG. 15 illustrates a flowchart detailing step 524 of the algorithm ofFIG. 5, in accordance with embodiments of the present invention. In step1502, the computing system associates the meta-object with operationalmetrics. In step 1504, the computing system associates the operationalmetrics with a key performance indicator. In step 1508, the computingsystem determines a key performance indicator by an analysis type. Instep 1512, the computing system determines reporting channels (andgenerates a report) having access to the operational metrics, the keyperformance indicator, and a context of said key performance indicator.The report comprises the operational metrics, the key performanceindicator, and the context of the key performance indicator.

FIG. 16 illustrates a flowchart detailing step 602 of the algorithm ofFIG. 6, in accordance with embodiments of the present invention. In step1602, the computing system discovers (i.e., using the API) contenttopics associated with the specified user accessible filter perspectivecontent accessible by the user. In step 1604, the computing systemretrieves a list comprising the content topics and associated logicalstorage rooms representations accessible by the user. In step 1608, thecomputing system selects (using the API) a first group of content topicsof the content topics and a first group of logical storage roomsrepresentations. In step 1610, the computing system selects (using theAPI) an X coordinate, a Y coordinate, and a Z coordinate. Each of the Xcoordinate, the Y coordinate, and the Z coordinate are representative bya hierarchal direction to a transverse. In step 1612, the computingsystem receives (using the API) a perspective parameter of the specifieduser accessible filter perspective content accessible by the user. Instep 1614, computing system performs an allowable operation on thespecified user accessible filter perspective content accessible by theuser.

FIG. 17 illustrates a flowchart detailing step 604 of the algorithm ofFIG. 6, in accordance with embodiments of the present invention. In step1702, the computing system discovers content topics associated with thespecified user accessible filter perspective content accessible by theuser. In step 1704, the computing system receives (i.e., from the user)a selection for a first topic of the content topics and enables accessto a specified logical storage room representation comprising firstcontent. The first content is associated with the first topic. In step1708, the computing system selects (i.e., in response to a userselection) an X coordinate, a Y coordinate, and a Z coordinate. The Xcoordinate, Y coordinate, and Z coordinate are each representative by ahierarchal direction to a transverse. In step 1710, the computing systemselects (in response to a user selection) a perspective view forpresenting the first content to the user. In step 1714, the computingsystem presents (to the user) the first content using the perspectiveview. Additionally, the computing system receives (from the user) aselection for modifying (e.g., updating or deleting) the first contentand modifies accordingly.

FIG. 18 illustrates a flowchart detailing step 608 of the algorithm ofFIG. 6, in accordance with embodiments of the present invention. In step1802, the computing system selects an X coordinate referenced to thespecified content. In step 1804, the computing system selects a Ycoordinate referenced to the specified content. In step 1808, thecomputing system selects a Z coordinate referenced to the specifiedcontent. In step 1810, the computing system cross-references the Xcoordinate, Y coordinate, and Z coordinate to an address internal to thecomputing system.

FIG. 19 illustrates a flowchart detailing step 610 of the algorithm ofFIG. 6, in accordance with embodiments of the present invention. In step1902, the computing system selects a specified storage room associatedwith the specified content. In step 1904, the computing system selectsan X coordinate, a Y coordinate, and a Z coordinate associated with thespecified content. In step 1908, the computing system selects aperspective view for presenting the specified content to the user. Theperspective view is associated with the X coordinate, the Y coordinate,and the Z coordinate. In step 1910, the computing system determines allusers accessing the specified content. In step 1912, the computingsystem filters the specified content.

FIG. 20 illustrates an application framework 2000 implemented by system5 of FIG. 1, in accordance with embodiments of the present invention.Data retrieval, storage, and data resource management planning (e.g.,procurement, provisioning, capacity planning, space management etc.) areeach represented in separate hierarchical taxonomies. Each node on thetaxonomy represents a room. The hierarchical taxonomy is segmented byits interdependency relationship intersections to other taxonomies. Thetaxonomies are addressable by internal REST style addressing, whichrepresents thee hierarchical taxonomies. URI addressing invokes a DOORSsystem of data access components exposed as services via service agents.Each DOOR service per each type of data storage comprises a data typechannel integration pattern. Therefore, by using a separate data typechannel for each type of data source, all of messages on a given channelwill comprise a same type of data. Additionally, the messages arecarried within a standardized envelope wrapper comprising a header ofoperational metadata and a body comprises data services transactionaldata. The envelope wrapper structure provides a canonical model for alldata services messages by providing a standardized metadata xmlhierarchical structure for all data services message representations.

Application framework comprises the following components:

1. A security component A: The security component A comprises a suite ofcommon services that implement a security policy enablingauthentication, authorization, secure communication, auditing, andprofile management as applied across all layers of the applicationarchitecture design.2. An operational management component B: The operational managementcomponent B comprises a suite of common services that implement anoperational management policy enabling ongoing, day-to-day running ofthe application and covers issues such as exception management,monitoring, business monitoring, metadata, configuration, and servicelocation as applied across all layers of the application architecturedesign.3. A communication management component C: The communication managementcomponent C comprises a suite of common services that implement acommunication integration standards policy which defines how allcomponents in an application will communicate with each other. Thecommunications policy includes, inter alia, communication synchronicity,format, and protocol.4. User interface (UI) components D1: User interface (UI) components D1represent a user facing a presentation layer of a software architecturedesign. User interfaces are implemented using screens, forms, additionalgraphical user interfaces (GUI), or additional technology used to renderand format data for users to acquire and validate data.5. User process components D2: User process components D2 enable userinteraction by driving a the process using separate user processcomponents. Therefore, the process flow and state management logic isnot hard-coded in a user interface elements themselves.6. Metadata integration layer component E: Metadata integration layercomponent E represents a canonical model (standardize data exchange)integration between architectural layers.7. Service interface component F: Service interface component F supportscommunication contracts (e.g., message-based communication, formats,protocols, security, exceptions, etc) required by consumers. Forexample, a credit card authorization service must expose a serviceinterface that describes a functionality offered by a service andrequired communication semantics for calling it.8. Business workflow component G1: Business workflow component G1defines and coordinates long running, multi-step business processes andmay be implemented using business process management tools.9. Business components G2: Business components G2 implement businesslogic (e.g., implement business rules, perform business tasks, etc) ofan application. For example, in a retail application, a user mustimplement a functionality that calculates a total price of goods orderedand add an appropriate delivery charge.10. Business entity components G3: Business entity components G3implement business entities using custom object-oriented classes thatrepresent real-world entities.11. DOORS access bus component H1: The DOORS access bus component H1comprises an addressable service interface that exposes interestingaspects of a data set through a reference to its resources. Eachresource (i.e., a meta-object) has its own unique URI. The URI is alogical link reference to an underlying accessed resource and enables anapplication using the DOORS data access layer, a URI interface via aDOORS application programming interface (API). The API translates a URIinterface passed parameter to DOOR data access layer logical componentH2 (i.e., a next layer of the DOORS data access layer).12. DOORS data access logic components H2: DOORS data access logiccomponents H2 allow applications and services access to a data store.DOORS data access layer logic components (H2) are intelligently aware(after a translation of a request from H1) of: what is being requested,what the user has access to, where the information is located,additional relevant information pertinent to the request, and throughwhat perspective viewpoint it should retrieve and/or store theinformation to or from a plurality of storage media sources and/orphysical storage locations. For example, a retail application mustretrieve product data from a database to display product details to auser and insert order details into a database when a user places anorder. DOORS data access logic components H2 abstracts logic necessaryto access data in a separate layer of data access logic componentsthereby centralizing data access functionality through uniqueintelligent capabilities.13. DOORS service agent component H3: DOORS service agent component H3manages the semantics of coordinating communication between the DOORSdata access layer logic components H2 and a particular remote service(e.g., when a business component must use functionality provided in anexternal service). For example, business components of a retailapplication may use a service agent to manage communication with acredit card authorization service and use a second service agent tohandle conversations with a courier service. DOORS service agentcomponent H3 isolates idiosyncrasies of calling diverse services from anremote application and provides additional services (helper service)such as, inter alia, pre-processing a basic mapping between a format ofdata exposed by a service and a format that an application using theDOORS Data Access Layer requires.14. Integration pattern component I: Integration pattern component Irepresents how (low level design methods deployed) to establishintegration between a data access layer and a DOORS service buscomponent J1.15. A DOORS service bus component J1: A DOORS service bus component J1provides an abstraction layer on top of an implementation of anenterprise event-driven and standards-based messaging engine. A DOORSservice bus component J1 provides common services such as, inter alia,mediation, intelligent routing, transformation, and protocol bridging.16. Cache L1 comprises a CPU attached memory.17. Process component L2 comprises a separate instanced memory residentCPU set of instruction enablement.18. Message queue L3 comprises a coordination of persisting and passingof control of stacked message content.19. Database L4 comprises a collection of information that is organizedfor easy access and management. Database L4 is updated via storagetables.20. Mailbox L5 comprises an electronic post office storage of emailmessages.21. X.500 directory services L6 comprises a single directory informationtree (DIT). A DIT comprises a hierarchical organization of entriesdistributed across one or more servers.22. File system L7 comprises instructions for enabling a method forstoring and organizing computer files and data contained in directoriesand subdirectories.23. Disk L8 comprises electronic storage consisting of magnetic mediacomprising tracks, sectors, and cylinders partitioned and indexed forconvenient data retrieval.

FIG. 21 illustrates a computer apparatus 90 (e.g., computing system 10of FIG. 1) used for storing and retrieving distributed data, inaccordance with embodiments of the present invention. The computersystem 90 comprises a processor 91, an input device 92 coupled to theprocessor 91, an output device 93 coupled to the processor 91, andmemory devices 94 and 95 each coupled to the processor 91. The inputdevice 92 may be, inter alia, a keyboard, a software application, amouse, etc. The output device 93 may be, inter alia, a printer, aplotter, a computer screen, a magnetic tape, a removable hard disk, afloppy disk, a software application, etc. The memory devices 94 and 95may be, inter alia, a hard disk, a floppy disk, a magnetic tape, anoptical storage such as a compact disc (CD) or a digital video disc(DVD), a dynamic random access memory (DRAM), a read-only memory (ROM),etc. The memory device 95 includes a computer code 97. The computer code97 includes algorithms (e.g., the algorithms of FIGS. 5-19) for storingand retrieving distributed data. The processor 91 executes the computercode 97. The memory device 94 includes input data 96. The input data 96includes input required by the computer code 97. The output device 93displays output from the computer code 97. Either or both memory devices94 and 95 (or one or more additional memory devices not shown in FIG.21) may comprise the algorithms of FIGS. 5-19 and may be used as acomputer usable medium (or a computer readable medium or a programstorage device) having a computer readable program code embodied thereinand/or having other data stored therein, wherein the computer readableprogram code comprises the computer code 97. Generally, a computerprogram product (or, alternatively, an article of manufacture) of thecomputer system 90 may comprise said computer usable medium (or saidprogram storage device).

Still yet, any of the components of the present invention could becreated, integrated, hosted, maintained, deployed, managed, serviced,etc. by a service provider who offers to for store and retrievedistributed data. Thus the present invention discloses a process fordeploying, creating, integrating, hosting, maintaining, and/orintegrating computing infrastructure, comprising integratingcomputer-readable code into the computer system 90, wherein the code incombination with the computer system 90 is capable of performing amethod for storing and retrieving distributed data. In anotherembodiment, the invention provides a business method that performs theprocess steps of the invention on a subscription, advertising, and/orfee basis. That is, a service provider, such as a Solution Integrator,could offer to store and retrieve distributed data. In this case, theservice provider can create, maintain, support, etc. a computerinfrastructure that performs the process steps of the invention for oneor more customers. In return, the service provider can receive paymentfrom the customer(s) under a subscription and/or fee agreement and/orthe service provider can receive payment from the sale of advertisingcontent to one or more third parties.

While FIG. 21 shows the computer system 90 as a particular configurationof hardware and software, any configuration of hardware and software, aswould be known to a person of ordinary skill in the art, may be utilizedfor the purposes stated supra in conjunction with the particularcomputer system 90 of FIG. 21. For example, the memory devices 94 and 95may be portions of a single memory device rather than separate memorydevices.

While embodiments of the present invention have been described hereinfor purposes of illustration, many modifications and changes will becomeapparent to those skilled in the art. Accordingly, the appended claimsare intended to encompass all such modifications and changes as fallwithin the true spirit and scope of this invention.

1. A method comprising: defining, by a computing system, a useraccessible meta-object referencing contextual content, wherein said useraccessible meta-object comprises a functional operation referencedobject, a service referenced object, or a content specific referencedobject; defining, by said computing system from a schema basedstructured definition for said user accessible meta-object, a predefineduser access content mapped hierarchical taxonomy and a configurationdata map associated with said predefined user access content mappedhierarchical taxonomy; creating, by a processor of said computingsystem, required content for said computing system, wherein said contentcomprises user accessible contextual content associated with saidpredefined user access content mapped hierarchical taxonomy;associating, by said computing system, user accessible topics ofrelevant tangible content of said content with specified logical storageroom representations, wherein each storage room of said specifiedlogical storage room representations comprises contextual contentstorage address spaces; generating, by said computing system, asearchable record entry associated with said user accessible topics andsaid specified logical storage room representations; associating, bysaid computing system, reference coordinates with said predefined useraccess content mapped hierarchical taxonomy, wherein said referencecoordinates are associated with said specified logical storage roomrepresentations; determining, by said computing system, a changeassociated with a relative point of view associated with each node ofsaid predefined user access content mapped hierarchical taxonomy;updating, by said computing system, said configuration data map, whereinsaid updating said configuration data map comprises generating updatedconfiguration data, wherein said updated configuration data comprisesreference coordinate pointers pointing to the contextual content storageaddress spaces, and wherein the contextual content storage addressspaces are comprised by a plurality of different storage mediums and aplurality of different physical storage locations; generating, by saidcomputing system, a uniform resource identifier (URI) associated withsaid content enabling a direct internal access mapping to the contextualcontent storage address spaces associated with reference coordinatepointers; determining, by said computing system, metering charges forusage of an account per paid subscription to the user accessiblecontextual content; applying, by said computing system, key performanceindicators to transactional analysis usage patterns of said useraccessible contextual content; presenting, by said computing system viaa dashboard view, analysis of a generated report associated with saidaccount, said transactional analysis usage patterns, and said usage. 2.The method of claim 1, wherein said defining said user accessiblemeta-object comprises: defining, by said computing system, a namespacefor said user accessible meta-object; defining, by said computingsystem, a domain for said namespace; defining, by said computing system,a sub-domain associated with said domain; classifying, by said computingsystem, a type for said user accessible meta-object; defining, by saidcomputing system, attributes for said user accessible meta-object; anddefining, by said computing system, URI mapping data associated withsaid URI.
 3. The method of claim 1, wherein said defining said schemabased structured definition comprises: defining, by said computingsystem, elements associated with said schema based structureddefinition; and defining, by said computing system, attributesassociated with said elements.
 4. The method of claim 1, wherein saiddetermining that content is required comprises: determining, by saidcomputing system, a content type for said content; determining, by saidcomputing system, a sub-domain associated with said user accessiblemeta-object; determining, by said computing system, a domain associatedwith said sub-domain; determining, by said computing system, a namespaceassociated with said domain; and generating, by said computing system,an entry in a provisioning table, wherein said entry is associated withsaid content.
 5. The method of claim 1, wherein said creating saidcontent comprises: updating, by said computing system, said predefineduser access content mapped hierarchical taxonomy with said topic;updating, by said computing system, said predefined user access contentmapped hierarchical taxonomy with elements associated with said schemabased structured definition; and updating, by said computing system,said predefined user access content mapped hierarchical taxonomy withattributes associated with said elements.
 6. The method of claim 1,wherein said associating said user accessible topics of relevanttangible content with said specified logical storage roomrepresentations comprises: determining, by said computing system, ifsaid specified logical storage room representations exist.
 7. The methodof claim 1, wherein said reference coordinate pointers comprise anX-coordinate, a Y-coordinate, and a Z-coordinate, and wherein saidassociating said reference coordinates with said predefined user accesscontent mapped hierarchical taxonomy comprises: determining, by saidcomputing system, an X-pointer associated with said predefined useraccess content mapped hierarchical taxonomy; determining, by saidcomputing system, a Y-pointer associated with said predefined useraccess content mapped hierarchical taxonomy; and determining, by saidcomputing system, a Z-pointer associated with said predefined useraccess content mapped hierarchical taxonomy.
 8. The method of claim 7,wherein said updating said configuration data comprises: associating, bysaid computing system, said X-coordinate, said Y-coordinate, and saidZ-coordinate with said X-pointer, said Y-pointer, and said Z-pointer,respectively.
 9. The method of claim 1, wherein said generating said URIcomprises: selecting, by said computing system, access point doorsassociated with said specified logical storage room representations;selecting, by said computing system, a first logical storage roomrepresentation of said specified logical storage room representations;determining, by said computing system, a plurality of meta-objectsassociated with said first logical storage room representation;determining, by said computing system, a plurality of sub-domainsassociated with said plurality of meta-objects; determining, by saidcomputing system, a plurality of domains associated with said pluralityof sub-domains; determining, by said computing system, a namespaceassociated with said plurality of domains; generating, by said computingsystem, a path associated with said URI; and generating, by saidcomputing system, an entry in a meta-object repository, wherein saidentry is associated with said URI.
 10. The method of claim 1, whereinsaid generating said account comprises: associating, by said computingsystem, said account to a plurality of objects for access; andassociating, by said computing system, said account to said user. 11.The method of claim 1, wherein said determining said metering chargescomprises: determining, by said computing system, a plurality ofaccounts that have access to said specified logical storage roomrepresentations; calculating, by said computing system, an accountaccess time for a plurality of objects associated with said specifiedlogical storage room representations; calculating, by said computingsystem, said metering charges by multiplying said account access time bya rate charged for access to said specified logical storage roomrepresentations; associating, by said computing system, said accountwith said usage; and generating, by said computing system, an invoiceassociated with said metering charges.
 12. The method of claim 1,wherein said generating said report comprises: associating, by saidcomputing system, said meta-object with operational metrics;associating, by said computing system, said operational metrics with akey performance indicator; determining, by said computing system, a keyperformance indicator by an analysis type; and determining, by saidcomputing system, reporting channels having access to said operationalmetrics, said key performance indicator, and a context of said keyperformance indicator, wherein said report comprises said operationalmetrics, said key performance indicator, and said context of said keyperformance indicator.
 13. The method of claim 1, wherein said referencecoordinates are associated with a hardware infrastructure referencestorage of said content or a general user specific storage of saidcontent.
 14. A process for supporting computer infrastructure, saidprocess comprising providing at least one support service for at leastone of creating, integrating, hosting, maintaining, and deployingcomputer-readable code in a computing system, wherein the code incombination with the computing apparatus is capable of performing themethod of claim
 1. 15. A computing apparatus comprising a processorcoupled to a computer-readable memory unit, said memory unit comprisinginstructions that when executed by the processor implements a methodcomprising: defining, by said computing system, a user accessiblemeta-object referencing contextual content, wherein said user accessiblemeta-object comprises a functional operation referenced object, aservice referenced object, or a content specific referenced object;defining, by said computing system from a schema based structureddefinition for said user accessible meta-object, a predefined useraccess content mapped hierarchical taxonomy and a configuration data mapassociated with said predefined user access content mapped hierarchicaltaxonomy; creating, by a processor of said computing system, requiredcontent for said computing system, wherein said content comprises useraccessible contextual content associated with said predefined useraccess content mapped hierarchical taxonomy; associating, by saidcomputing system, user accessible topics of relevant tangible content ofsaid content with specified logical storage room representations,wherein each storage room of said specified logical storage roomrepresentations comprises contextual content storage address spaces;generating, by said computing system, a searchable record entryassociated with said user accessible topics and said specified logicalstorage room representations; associating, by said computing system,reference coordinates with said predefined user access content mappedhierarchical taxonomy, wherein said reference coordinates are associatedwith said specified logical storage room representations; determining,by said computing system, a change associated with a relative point ofview associated with each node of said predefined user access contentmapped hierarchical taxonomy; updating, by said computing system, saidconfiguration data map, wherein said updating said configuration datamap comprises generating updated configuration data, wherein saidupdated configuration data comprises reference coordinate pointerspointing to the contextual content storage address spaces, and whereinthe contextual content storage address spaces are comprised by aplurality of different storage mediums and a plurality of differentphysical storage locations; generating, by said computing system, auniform resource identifier (URI) associated with said content enablinga direct internal access mapping to the contextual content storageaddress spaces associated with reference coordinate pointers;determining, by said computing system, metering charges for usage of anaccount per paid subscription to the user accessible contextual content;applying, by said computing system, key performance indicators totransactional analysis usage patterns of said user accessible contextualcontent; presenting, by said computing system via a dashboard view,analysis of a generated report associated with said account, saidtransactional analysis usage patterns, and said usage.
 16. The computingapparatus of claim 15, wherein said defining said user accessiblemeta-object comprises: defining, by said computing system, a namespacefor said user accessible meta-object; defining, by said computingsystem, a domain for said namespace; defining, by said computing system,a sub-domain associated with said domain; classifying, by said computingsystem, a type for said user accessible meta-object; defining, by saidcomputing system, attributes for said user accessible meta-object; anddefining, by said computing system, URI mapping data associated withsaid URI.
 17. The computing apparatus of claim 15, wherein said definingsaid schema based structured definition comprises: defining, by saidcomputing system, elements associated with said schema based structureddefinition; and defining, by said computing system, attributesassociated with said elements.
 18. The computing apparatus of claim 15,wherein said determining that content is required comprises:determining, by said computing system, a content type for said content;determining, by said computing system, a sub-domain associated with saiduser accessible meta-object; determining, by said computing system, adomain associated with said sub-domain; determining, by said computingsystem, a namespace associated with said domain; and generating, by saidcomputing system, an entry in a provisioning table, wherein said entryis associated with said content.
 19. The computing apparatus of claim15, wherein said creating said content comprises: updating, by saidcomputing system, said predefined user access content mappedhierarchical taxonomy with said topic; updating, by said computingsystem, said predefined user access content mapped hierarchical taxonomywith elements associated with said schema based structured definition;and updating, by said computing system, said predefined user accesscontent mapped hierarchical taxonomy with attributes associated withsaid elements.
 20. A computer program product, comprising a computerreadable storage device storing a computer readable program code, saidcomputer readable program code configured to perform method upon beingexecuted by a computer processor of a computing system, said methodcomprising: defining, by said computing system, a user accessiblemeta-object referencing contextual content, wherein said user accessiblemeta-object comprises a functional operation referenced object, aservice referenced object, or a content specific referenced object;defining, by said computing system from a schema based structureddefinition for said user accessible meta-object, a predefined useraccess content mapped hierarchical taxonomy and a configuration data mapassociated with said predefined user access content mapped hierarchicaltaxonomy; creating, by a processor of said computing system, requiredcontent for said computing system, wherein said content comprises useraccessible contextual content associated with said predefined useraccess content mapped hierarchical taxonomy; associating, by saidcomputing system, user accessible topics of relevant tangible content ofsaid content with specified logical storage room representations,wherein each storage room of said specified logical storage roomrepresentations comprises contextual content storage address spaces;generating, by said computing system, a searchable record entryassociated with said user accessible topics and said specified logicalstorage room representations; associating, by said computing system,reference coordinates with said predefined user access content mappedhierarchical taxonomy, wherein said reference coordinates are associatedwith said specified logical storage room representations; determining,by said computing system, a change associated with a relative point ofview associated with each node of said predefined user access contentmapped hierarchical taxonomy; updating, by said computing system, saidconfiguration data map, wherein said updating said configuration datamap comprises generating updated configuration data, wherein saidupdated configuration data comprises reference coordinate pointerspointing to the contextual content storage address spaces, and whereinthe contextual content storage address spaces are comprised by aplurality of different storage mediums and a plurality of differentphysical storage locations; generating, by said computing system, auniform resource identifier (URI) associated with said content enablinga direct internal access mapping to the contextual content storageaddress spaces associated with reference coordinate pointers;determining, by said computing system, metering charges for usage of anaccount per paid subscription to the user accessible contextual content;applying, by said computing system, key performance indicators totransactional analysis usage patterns of said user accessible contextualcontent; presenting, by said computing system via a dashboard view,analysis of a generated report associated with said account, saidtransactional analysis usage patterns, and said usage.